Skip to main content
POST
Get memories [OSS + Cloud]

Authorizations

Authorization
string
header
required

API key issued by EverOS, sent as Authorization: Bearer <api_key>.

Body

application/json
memory_type
enum<string>
required

Which kind of memory to list: "episode" (narrative summaries of past sessions), "profile" (stable identity and preferences), "agent_case" (a distilled past trajectory) or "agent_skill" (a reusable skill). It must match the owner — the mismatched pairings are rejected with 422.

Available options:
episode,
profile,
agent_case,
agent_skill
app_id
string
default:default

Scope to read from, defaulting to "default". Must match the pair used on write.

Maximum string length: 128
project_id
string
default:default

Second half of the scope, defaulting to "default".

Maximum string length: 128
user_id
string | null

Read one user's memories. Exactly one of user_id / agent_id is required, and a user owner may only ask for "episode" or "profile".

Required string length: 1 - 256
agent_id
string | null

Read one agent's memories. Exactly one of user_id / agent_id is required, and an agent owner may only ask for "agent_case" or "agent_skill".

Required string length: 1 - 256
page
integer
default:1

1-based page number.

Required range: x >= 1
page_size
integer
default:20

Items per page, 1 to 100 (default 20).

Required range: 1 <= x <= 100
sort_by
enum<string>
default:timestamp

Order by "timestamp" (when the memory happened, default) or "updated_at" (when it was last written). Profiles and agent skills have no temporal column and always sort by "updated_at".

Available options:
timestamp,
updated_at
sort_order
enum<string>
default:desc

"desc" (default, newest first) or "asc".

Available options:
asc,
desc
with_readable_episode
boolean
default:false
deprecated

Deprecated and has no effect: the human-readable rendering it requested is no longer produced. Still accepted so existing clients that send it keep working; new code should leave it out.

filters
FilterNode · object | null

Optional filter tree applied to the listing; same shape as on search.

Response

Successful Response

request_id
string
required

Request trace id (peer to data)

data
GetData · object
required

Endpoint-defined business result